fix(core): scroll-spy for non-contiguous regions#2920
Closed
bennypowers wants to merge 7 commits intomainfrom
Closed
fix(core): scroll-spy for non-contiguous regions#2920bennypowers wants to merge 7 commits intomainfrom
bennypowers wants to merge 7 commits intomainfrom
Conversation
🦋 Changeset detectedLatest commit: 616bd75 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
✅ Deploy Preview for patternfly-elements ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
Contributor
✅ Commitlint tests passed!More Info{
"valid": true,
"errors": [],
"warnings": [],
"input": "fix(core): scroll-spy for non-contiguous regions"
} |
Contributor
Contributor
Contributor
zeroedin
approved these changes
Jul 22, 2025
Contributor
zeroedin
left a comment
zeroedin
left a comment
There was a problem hiding this comment.
linking gaps, targets managed
This was referenced Jul 25, 2025
Contributor
Contributor
Contributor
bennypowers
added a commit
that referenced
this pull request
Mar 8, 2026
Fixes three bugs in ScrollSpyController: 1. Rapid clicks: setActive() now cancels previous force state via AbortController before establishing new force, preventing stale listeners from releasing force prematurely. 2. Force release timing: replaced await-first-intersection approach with scrollend event listener (+ 3s safety timeout). The old approach released force when any IO fired during smooth scroll, causing intermediate sections to steal the active state. 3. Non-contiguous sections: passedLinks are now sorted by DOM order instead of relying on Set insertion order, which was unreliable when sections had untracked content between them. Also fixes a safeguard bug where the #nextIntersection timeout set `#intersected = false` (should be `true`), which could cause an infinite rAF loop, and fixes the boundary comparison to use rootBounds.top instead of intersectionRect.top so elements exactly at the viewport top are correctly considered "passed". Closes #2911 Closes #2920 Assisted-By: Claude Opus 4.6 <noreply@anthropic.com>
4 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
See RedHat-UX/red-hat-design-system#2471
What I did
Testing Instructions
Notes to Reviewers